Semiconductor memory device

ABSTRACT

According to one embodiment, a semiconductor memory device includes semiconductor memory chips in which data requested to be written. The data has one or more pieces of first data in a predetermined unit. The device includes a write controller that writes the first data and redundancy information calculated by using a predetermined number of pieces of the first data and used for correcting an error in the predetermined number of pieces of the first data into different semiconductor memory chips; and a storage unit that stores identification information and region specifying information so as to be associated with each other. The identification information associates the first data and the redundancy information, and the region specifying information specifies a plurality of storage regions in the semiconductor memory chips to which the pieces of the first data and the redundancy information associated with each other are written.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a divisional of U.S. application Ser. No. 13/868,620filed Apr. 23, 2013, which is a continuation of U.S. application Ser.No. 12/888,822 filed Sep. 23, 2010, and is based upon and claims thebenefit of priority from the prior Japanese Patent Application No.2010-029114, filed on Feb. 12, 2010; the entire contents of each ofwhich are incorporated herein by reference.

FIELD

Embodiments described herein relate generally to a semiconductor memorydevice.

BACKGROUND

It is known that probabilistic failures occur in a semiconductor storagechip. The failures include a failure of a memory cell such as a softerror caused by an alpha beam and a failure in a larger unit such as afailure in a read circuit or an input/output buffer (I/O buffer). For afailure in a memory cell, conventionally, by adding redundantinformation such as an Error correction code (ECC) to data, erroneousdata caused by the failure can be corrected within a predeterminednumber of errors in a predetermined unit. For a failure in a larger unitsuch as a failure in a reading circuit or an I/O buffer, the number oferrors is extremely large, and it is difficult to perform an errorcorrection by a realistic circuit scale.

In a system employing a number of Hard Disk Drives (HDDs), a failure inan HDD have become a problem. Redundant Array of Inexpensive Disks(RAID) is widely known as a technique for addressing such failure in theHDD unit basis by using an error correction code constituted by aplurality of HDDs (refer to, for example, “A Case for Redundant Arraysof Inexpensive Disks (RAID)”, UC Berkeley Technical ReportUCB/CSD-87-391, 1987). In this technique, by writing data to a pluralityof HDDs and storing redundant information obtained by using the datainto one of the HDDs, an error correction code is constituted by theplurality of HDDs. As a method of restoring data with RAIDs when aplurality of HDDs become faulty, a method in which a Reed Solomon codeis used is also known (refer to, for example, “A Tutorial onReed-Solomon Coding for Fault-Tolerance in RAID-like Systems”, James S.Plank, Technical Report CS-96-332, Department of Computer ScienceUniversity of Tennessee).

However, in a semiconductor memory device using a large number ofsemiconductor storage chips as memory chips, even when an errorcorrection code (ECC) for repairing a failure in a memory cell, thefailure in a memory chip cannot be prevented. As a result, it may becomea failure of the semiconductor memory device. To address a failure in amemory chip, it is considered to constitute an error correction code bya plurality of memory chips in a manner similar to HDDs. In this method,however, for each writing operation, writing to a memory chip in whichredundant information is written is performed for updating redundantinformation. Concretely, in RAIDs of HDDs, for example, when an errorcorrection code is constituted by four HDDs A, B, C, and D in which datais written and one HDD P in which redundant information is written, thewriting operation is performed as follows. If data is written in the HDDA out of the HDDs A, B, C, and D, writing to the HDD P is also performedfor updating redundant information.

Meanwhile, a semiconductor memory element of the NAND type (referred toas NAND memory) used for a semiconductor memory device is widely used asa semiconductor memory chip of a Solid State Drive (SSD) because thearea per bit is small and it is nonvolatile, but it is widely known thatthe number of write times is limited. Consequently, it is necessary toreduce the number of write times in order to increase design life of asemiconductor memory device.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram illustrating a hardware configuration of asemiconductor storage device 50 of an embodiment;

FIG. 2 is a conceptual diagram for explaining compaction;

FIG. 3 is a diagram illustrating a functional configuration of thesemiconductor storage device 50;

FIG. 4 is a diagram illustrating a data configuration of aforward-lookup table;

FIG. 5 is a diagram illustrating a data configuration of a bit vectortable;

FIG. 6 is a diagram illustrating data to be written;

FIG. 7 is a diagram for explaining writing operation performed byround-robin manner;

FIG. 8 is a diagram for explaining the configuration of an errorcorrecting code;

FIG. 9 is a flowchart showing a procedure of writing data to be written;

FIG. 10 is a diagram illustrating a state where data to be written iswritten with lapse of time;

FIG. 11 is a flowchart showing a procedure of reading data;

FIG. 12 is a diagram showing a state where data in which abnormalityoccurs is restored; and

FIG. 13 is a flowchart showing a procedure of compaction process.

DETAILED DESCRIPTION

In general, according to one embodiment, a semiconductor memory deviceincludes a plurality of semiconductor memory chips in which datarequested to be written by an information processing apparatus isdescribed. The data has one or more pieces of first data in apredetermined unit. The semiconductor memory device includes a writecontroller configured to write the pieces of the first data in thepredetermined unit and redundancy information into differentsemiconductor memory chips, the redundancy information being calculatedby using a predetermined number of pieces of the first data and beingused for correcting an error in the predetermined number of pieces ofthe first data; and a storage unit configured to store thereinidentification information and region specifying information so as to beassociated with each other, the identification information associatingthe predetermined number of pieces of the first data and the redundancyinformation, and the region specifying information specifying aplurality of storage regions in the semiconductor memory chips to whichthe pieces of the first data and the redundancy information associatedwith each other are written.

Exemplary embodiments of a semiconductor storage device will bedescribed in detail below with reference to the appended drawings.

A hardware configuration of the semiconductor memory device according tothe embodiment will be described with reference to FIG. 1. Asemiconductor memory device 50 includes a processor 51, a boot Read OnlyMemory (ROM) 52, an SATA/SAS interface 55, a memory controller 53, aDynamic Random Access Memory (DRAM) 54, NAND controllers 57A to 57F, aplurality of semiconductor memory elements (NAND) 58A to 58F, and a bus56 connecting those components. In the case where it is unnecessary todistinguish the NAND controllers 57A to 57F from one another, they maybe simply described as the NAND controllers 57. In the case where it isunnecessary to distinguish the semiconductor memory elements 58A to 58Ffrom one another, they may be simply described as the semiconductormemory elements 58.

The SATA/SAS interface 55 controls communication with a host as ahigh-order apparatus of the semiconductor memory device 50 under controlof the processor 51. The boot ROM 52 stores a program which is executedat the turn on the power source. Various system programs are stored inthe semiconductor memory elements 58. The processor 51 reads the programfrom the boot ROM 52 at the turn-on of the power source, executes it,transfers the various system programs stored in the semiconductor memoryelements 58 to the DRAM 54 in accordance with the program, and executesthe system program on the DRAM 54, thereby controlling the entiresemiconductor memory device 50 to realize various functions. Concretely,the processor 51 interprets a command sent from the host via theSATA/SAS interface 55 and, according to the command, controls writing ofdata to the semiconductor memory elements 58 and reading of data fromthe semiconductor memory elements 58.

The memory controller 53 controls the DRAM 54. The DRAM 54 storesvarious data and various programs. In the embodiment, the DRAM 54 storesa forward-lookup table and a bit vector table which will be describedlater. The NAND controllers 57 control the semiconductor memory elements58 and include an error correction circuit.

The semiconductor memory element 58 corresponds to a semiconductor chip.For example, it is a memory element used in an NAND-type flash memory.Such semiconductor memory elements 58 cannot read/write at random butcan perform reading/writing in unit called a page. A plurality of pagesform a storage region in unit called a block. It is assumed here thatone page is made of 4 KB, and one block is formed by 64 pages. Each ofthe semiconductor memory elements 58 is constituted by a plurality ofblocks. In the embodiment, as shown in FIG. 1, the number ofsemiconductor memory elements 58 is six. Channels (CH0 to CH5) areallocated to the semiconductor memory elements 58A to 58F, respectively.The channel (CH5) among the channels is allocated as a channel in whichredundant information is written, the other channels (CH0 to CH4) areallocated as channels in which data requested to be written by the hostis written. The pages of the channels CH0 to CH5 are used as a set toconstitute an error-correcting code. The channels CH0 to CH4 correspondto the semiconductor memory elements 58A to 58E, respectively, and thechannel CH5 corresponds to the semiconductor memory element 58F. As willbe described later, in the case where data requested to be written bythe host is larger than the size of a page, the semiconductor memorydevice 50 divides the data into a plurality of pieces, and allocates andwrites the data pieces divided in pages (referred to as divided piecesof data) to the respective channels CH0 to CH4. That is, in the basicconfiguration of the embodiment, the semiconductor memory device 50writes a predetermined number of pieces of data requested to be writtenin a predetermined unit and redundant information that is calculated byusing the pieces of data and is used for correcting an error of thepieces of the data into the different semiconductor memory elements 58,respectively, thereby constituting an error correction code by thepieces of data and the redundant information. As an error correctioncode, for example, a parity code is used.

Here, a write method for writing to the semiconductor memory elements 58will be described. A NAND-type semiconductor memory elementconventionally employs an Log-structured method. In the Log-structuredmethod, a block needs to be erased before writing. Erasure of a block isto set all bits constituting the block to “1”. The semiconductor memorydevice 50 performs such erasure in units of a block and performs writingin units of a page to the erased blocks. Accordingly, in the NAND-typesemiconductor memory elements 58, data can be sequentially written tounwritten pages in an erased block, and written pages cannot be addpages. Writing of data in response to the request from the host isindicated by a logical block address used in the host. On the otherhand, writing of data and redundant information to the semiconductormemory elements 58 is performed according to the physical blockaddresses of the semiconductor memory elements 58 in the ascending orderof pages regardless of the logical block address. The associationbetween the physical block address and the logical block address isstored in a forward lookup table described later. When writing of newdata is requested by the host with the logical block address specifiedin the previous data request being specified again, the semiconductormemory device 50 writes the new data to an unwritten page of an erasedblock. In this case, the page to which writing corresponding to thislogical block address is previously performed is set to be invalid andthe page to which the new data is written is set to be valid. Thesemiconductor memory device 50 writes new data and redundant informationwhile constructing the above-described error correction code.

In this Log-structured method, when the number of pages which are madeinvalid increases by continuing the writing, write realizable capacity(referred to as realizable capacity) in the semiconductor memoryelements 58 becomes smaller. At the time point when the number of newerased blocks to which information can be written, that is, the numberof blocks to which information is not written yet after erasure(referred to as free blocks), decreases and a set of blocks constitutingan error correction code (referred to as a logical block) cannot beassured, a write impossible state occurs. To prevent it, in thesemiconductor memory device 50, garbage collection is made at a propertiming. The garbage collection made in the semiconductor memory elements58 will be particularly called compaction. FIG. 2 is a conceptualdiagram for explaining compaction. The semiconductor memory device 50collects data written in physical block addresses (referred to as validdata) being not made invalid in blocks containing the pages being madeinvalid, and newly rewrites the collected valid data in free blocks tomove the valid data thereto. After that, the semiconductor memory device50 erases the blocks, thereby generating a new free block. In thesemiconductor memory device 50, blocks that were unwritable becomewritable again by performing such compaction, allowing free blocks to bereserved. That is, new free blocks are generated by performing thecompaction. Further if there is an unwritten page in a block in whichvalid data is written as a result of moving data, data can be newlywritten to the remaining unwritten page.

At least one free block is needed to perform such compaction, whichmeans that the capacity (referred to as implemented capacity)implemented in the NAND-type semiconductor memory element 58 is smallerthan the capacity at which writing can be actually realized. In theembodiment, the difference between the implemented capacity and therealizable capacity is referred to as spare capacity. When the sparecapacity is small, the semiconductor memory device 50 has to frequentlycarry out compaction, which has a great impact on performance thereof.Referring to FIG. 2, compaction on the block unit basis has beendescribed. In the embodiment, the logical block is the basic unit, sothat a free block is reserved for each channel to constitute a logicalblock, and the compaction is performed the logical block unit basis.

Next, functions implemented in the semiconductor memory device 50 willbe described with reference to FIG. 3. The semiconductor memory device50 includes a host interface unit 60, a buffer controller 61, an addresstranslation unit 62, a CH allocating unit 63, a compaction candidatedetector 64, a management table updating unit 65, NAND controllers 66Ato 66F, a data buffer 67, a compaction read queue 68, and a managementtable 69. The function of the host interface unit 60 is realized byexecution of the program by the processor 51 and the function of theSATA/SAS interface 55. The functions of the address translation unit 62,the CH allocating unit 63, the management table updating unit 65, thecompaction candidate detector 64, and the buffer controller 61 areimplemented when the processor 51 executes the program. The functions ofthe NAND controllers 66A to 66F correspond to the NAND controllers 57Ato 57F, respectively and implemented by execution of the program by theprocessor 51 and the functions of the NAND controllers 57A to 57Fcorresponding to the NAND controllers 66A to 66F, respectively. The NANDcontrollers 66A to 66F correspond to the semiconductor memory elements58A to 58F to which the channels CH0 to CH5 are allocated, respectively,in a one-to-one corresponding manner. In the case where it isunnecessary to distinguish the NAND controllers 66A to 66F from oneanother, they may be simply described as the NAND controllers 66. Thedata buffer 67, the compaction read queue 68, and the management table69 are, for example, information stored on the DRAM 54.

The host interface unit 60 is an interface that controls communicationbetween the host and the semiconductor memory device 50. The hostinterface unit 60 receives a command transmitted from the host. When thecommand requests writing of data with a specified logical block address,the host interface unit 60 transmits the command (referred to as writecommand) to the address translation unit 62 which will be describedlater. When the size of the data requested to be written is equal to orless than the page size, the host interface unit 60 transmits the datato the buffer controller 61, which will be described later. When thesize of the data is larger than the page size, the host interface unit60 divides the data into pieces of units of a page, and sends the datathus divided (referred to as divided pieces of data) to the buffercontroller 61. This is because the translation between the logical blockaddress and the physical block address is made in the page unit basis.For example, the host interface unit 60 divides data of 128 KB into 32pieces of 4-KB data. The data or the divided pieces of data transmittedto the buffer controller 61 in response to the write command is referredto as write target data for convenience of description.

In the case where a command transmitted from the host requests readingof data with a specified logical block address, if the size of the datarequested to be read is equal to or less than the page size, the hostinterface unit 60 sends the command (referred to as the read command) tothe address translation unit 62. In the case where the size of datarequested to be read is larger than the page size, the host interfaceunit 60 sends a command (read command) requesting reading of data on thepage unit basis to the address converter 62. The host interface unit 60calculates the logical block address of each of pieces of data to beread by using the logical block address specified by the commandtransmitted from the host, and sends the read command requesting to readdata with the calculated logical block address to the addresstranslation unit 62. The host interface unit 60 reads the data to beread which is stored in a designated region in the data buffer 67 by thebuffer controller 61, which will be described later, and transmits it tothe host.

The management table 69 includes the forward-lookup table and the bitvector table. The forward-lookup table is stored therein identificationinformation and region specifying information associated each other. Theidentification information is for associating data to be written andredundancy information, and the region specifying information specifieseach of a plurality of storage regions in the semiconductor memoryelements 58 in which the data to be written and the redundancyinformation associated with each other are written. The forward-lookuptable indicates the association between the logical address of data tobe written and the physical address indicative of a physical storagelocation in which the data to be written is stored in the semiconductorstorage elements 58. Such a forward-lookup table is used at the time ofspecifying the physical address indicative of the location on thesemiconductor storage element 58 in which data corresponding to thelogical address specified by the host is stored. FIG. 4 is a diagramshowing the data configuration of the forward-lookup table. As shown inFIG. 4, the forward-lookup table has an LBA table and alogical-to-physical conversion table. The LBA table includes the logicaladdress as an index and entries including the channel number, the pagenumber given to the page, and the logical block number given to alogical block in which the data is stored.

The logical block number is identification information that associateswrite target physical blocks and redundant information physical blockwith each other. The logical block number, which is a unique number, isgiven to each of the blocks in the sequence they were generated. Thechannel number are CH0 to CH4 in this embodiment, and indicates to whichchannel the semiconductor memory element 58 including the physical blockin which data associated with the logical block address is stored isconnected. The page number indicates which page of the physical blockidentified by the logical block number and the channel number the dataassociated with the logical block address is stored in. The page numbermay be given in the sequence of the physical block addresses, or thephysical block address itself may be given as the page number, forexample.

The logical-physical translation table is region specifying informationspecifying a plurality of storage regions in the semiconductor memoryelements 58 in which write target data and redundant information are tobe written, and stores therein the logical block number and the physicalblocks of channels associated with the logical block so as to becorresponded to each other. The logical-to-physical translation tablestores therein the logical block number as an index, addresses ofphysical blocks of the channels (physical block addresses) beingassociated with the logical block are stored. In such a configuration,using, as an index, the logical block number stored in entries in theLBA table corresponding to one logical block address, an entry in thelogical-to-physical translation table relating to the logical block isspecified with the index. Next, a physical block in the semiconductormemory element 58 connected to the channel of the channel numberrecorded in the entry in the LBA table is specified from among thephysical blocks stored in the entries in the logical-to-physicaltranslation table. The page in which the data corresponding to thelogical block address is written is specified with the page numberincluded in the entry in the LBA table.

As described above, the data required by the host to be written isstored in the channels CH0 to CH4 on the page unit basis, and redundantinformation that is to be added to constitute an error correction codeis written in the channel CH5. Consequently, the redundant informationis written in the storage region of the physical block address of thechannel CH5 indicated by each of entries in the logical-to-physicaltranslation table. Since the logical block address corresponding to theredundant information does not exist, an entry relating to the redundantinformation is not recorded in the LBA table. Information on redundantinformation is recorded in an entry in the logical-to-physicaltranslation table. The forward-lookup table is updated each time writetarget data and redundant information are written in the semiconductormemory element 58. How the forward-lookup table is updated will bedescribed later.

Next, the bit vector table will be described with reference to FIG. 5.The bit vector table is a table showing, in binary in the sequence ofphysical blocks, which pages in each of the physical blocks on each ofthe channels CH0 to CH4 out of the physical blocks associated with thelogical block are pages (referred to as valid pages) to which valid dataare written. The binary indication for each page is called a bit vector.If the value of the bit vector is “1”, this means that the page is avalid page, and if the value of the bit vector is “0”, this means thatthe page is not a valid page (invalid). In the initial state, the valuesof bit vectors are all set to “0”.

In the embodiment, channels to which write target data is written arefive channels CH0 to CH4 out of the physical blocks associated with thelogical block, and if it is assumed that one physical block includes 64pages, one logical block includes 320 pages. Consequently, the number ofcorresponding bit vectors is 320 per logical block. As shown in FIG. 5,the bit vector table includes, for each logical block, theabove-described logical block number as the index thereof, the bitvector associated with each page included in each of the physical blocksof the channels CH0 to CH4 associated with the logical block to whichthe logical block number is given, and a counter. In the embodiment, theentries in the logical-to-physical translation table and the bit vectorin the bit vector table are arranged in advance so that the index in thelogical-to-physical translation table matches the index in the bitvector table match. In FIG. 5, the bit vectors are arranged in thesequence of the pages of each of the physical blocks of the channels CH0to CH4 in such a manner that, from left, the first page, the secondpage, . . . , and the last page of the channel CH0, the first page, thesecond page, . . . , and the last page of the channel CH1, and the like.The counter represents the total number of bit vectors whose values are“1”. Since a page whose corresponding bit vector has a value “1” is avalid page, the counter represents the number of valid pages in alogical block. In such a configuration, the bit vector table is updatedeach time the host requests writing of data. How the bit vector table isupdated will be described later.

The description refers back to FIG. 3. The address translation unit 62receives a command from the host interface unit 60. When the command isa read command, the address translation unit 62 refers to theforward-lookup table in the management table 69 using the logical blockaddress specified by the read command, and determines a channel and aphysical block address of a page in which data requested to be read bythe read command is written. The address translation unit 62 specifies achannel and a physical block address and sends a command requesting toread data to the NAND controller 66 via the CH allocating unit 63. Incontrast, when the command received from the host interface unit 60 is awrite command, the address translation unit 62 sends the write commandto the CH allocating unit 63 which will be described later.

In response to a compaction read command stored in the compaction readqueue 68 which will be described later, the address translation unit 62sends a command requesting to read data (valid data) in a valid pagewith a physical address specified by the compaction read command to theNAND controller 66 corresponding to the channel to which thesemiconductor memory element 58 with the physical block including thevalid page is connected, by referring to the forward-lookup table. Thevalid data is read from the semiconductor memory element 58 via the NANDcontroller 66 and stored in the data buffer 67 via the buffer controller61. The address translation unit 62 sends the command requesting towrite the valid data (referred to as compaction write command) to the CHassigning unit 63.

The CH allocating unit 63 receives the command from the addresstranslation unit 62, and when the command is a write command, determinesthe channel to which write target data is to be written. For example,the CH allocating unit 63 performs writing operation in round-robinmanner in 4 KB in channels other than the channel to which redundantinformation is written (in this case, the channel CH5) and determinesthe channel to which data is written in accordance with the order ofround robin. Then, the CH allocating unit 63 sends the commandrequesting to write the write target data to the NAND controller 66corresponding to the determined channel. In contrast, in the case wherereading of data is requested with a specified channel and a specifiedphysical block address by a command from the address translation unit62, a command requesting to read data with the specified physical blockaddress is transmitted to the NAND controller 66 corresponding to thedesignated channel. In the case where a command received from theaddress translation unit 62 is a compaction write command, the CHallocating unit 63 determines a channel to which data is to be writtenin accordance with the order of round robin and sends a commandrequesting to write valid data to the NAND controller 66 correspondingto the determined channel.

The NAND controller 66 receives the command from the CH allocating unit63 and accesses the corresponding semiconductor memory element 58according to the command. Concretely, when the command requests to writedata, the NAND controller 66 obtains write target data via the buffercontroller 61 and writes the write target data to the semiconductormemory element 58. In the writing, the NAND controller 66 sets a writepointer to sequentially point a writing location, page by page, out ofunwritten page in an erased block of the corresponding semiconductormemory element 58, writes the write target data to a page at a locationpointed by the write pointer, and then updates the write pointer topoint a location of an unwritten page which is the next page subsequentto the page subjected to the writing. Therefore, the value of the writepointer changes to sequentially point the next write location. Forexample, when a block is identified by a physical block address of 15bits in each channel and the block includes 64 pages, the write pointerhas 15+6=21 bits in total.

Here, the data configuration of write target data and redundantinformation will now be described. The NAND controller 66 adds an errorcorrection code (referred to as page ECC) for detecting and correctingan error of the write target data itself and a logical block addressspecified by a write command to the write target data. It is assumedthat the page ECC includes codes such as a CRC code for detecting anerror in data and an ECC code to correct the data error. The reason whythe page ECC also includes a CRC code is that there is the possibilityof miss-correction when the data is corrected to the wrong data. FIG. 6is a diagram illustrating write target data to which redundantinformation is added. In the semiconductor memory elements 58 of thechannels determined as described above, the NAND controller 66 writesthe write target data to which such a page ECC and the logical blockaddress are added to a page pointed by the write pointer in thesemiconductor memory element 58 in each channel determined as describedabove. The write target data has a size in a unit of pages. It isassumed that the page size of the semiconductor memory element 58 equalsthe size of the entire data including the write target data and theadded page ECC and logical block address. The logical block address ofeach of divided pieces of data is calculated by each NAND controller 66on the basis of the logical block address specified by the writecommand. In contrast, the NAND controller 66F corresponding to thechannel CH5 to which redundant information calculated so as toconstitute the error correction code is written adds the page ECC fordetecting and correcting an error of redundant information itself to theredundant information. The NAND controller 66F writes the redundantinformation to which the page ECC is added into the page in thesemiconductor memory element 58F pointed by the write pointer.

Next, writing of a plurality of divided pieces of data as write targetdata to the channels CH0 to CH5 by round-robin processing will bedescribed. FIG. 7 is a diagram for explaining writing performed by theround-robin processing. For simplification of the diagram, the logicalblock addresses added to the divided pieces of data are not shown. Asshown in the diagram, the divided pieces of data is written sequentiallyin the round-robin manner from the channel CH0 to the channel CH4 in amanner such that first divided data D1 is written to the channel CH0 attime T1 and the next divided data D2 is written to the channel CH1 attime T2. When divided data D5 is written in the channel CH4 at time T5,parity P of the divided data D1 written in the channel CH0 at time T1,the divided data D2 written in the channel CH1 at time T2, the divideddata D3 written in the channel CH2 at time T3, the divided data D4written in the channel CH3 at time T4, and parity P of the divided dataD5 written in the channel CH4 at time T5 is calculated as redundantinformation, and the redundant information P is written in the channelCH5. At the time of further writing of divided pieces of data, the datais written sequentially in the round-robin manner from the channel CH0.By writing the divided pieces of data in the round-robin manner, writingoperation of the channels are uniformly performed. In the example of thediagram, a state where data is written in order of the channels withlapse of time is shown. However, the invention is not limited to theexample. Data may be written simultaneously to two or more channels.

Next, the configuration of the error correction code will be describedwith reference to FIG. 8. For convenience of explanation, in thediagram, the logical block addresses added to the divided pieces of datato be written in each of the channels CH0 to CH4 are not shown. As shownin FIG. 8, the NAND controller 66F corresponding to the channel CH5calculates the exclusive OR in bytes at the same offset location inpieces of data written in the channels CH0 to CH4, and writes the valuethus calculated as redundant information in the same offset location inthe semiconductor memory element 58F of the channel CH5. That is, anerror correction code is constituted by the bytes at the same offsetlocation in the channels CH0 to CH5.

The description refers back to FIG. 3. When the command received fromthe CH allocating unit 63 requests to read data with a specifiedphysical block address, the NAND controller 66 reads data from alocation corresponding to the physical block address in thesemiconductor memory element 58 using the physical block address, andsends the read data to the buffer controller 61. If there is an error inthe data read from the semiconductor memory element 58, the NANDcontroller 66 detects the error and corrects it. A method of detectingand correcting an error in data will be described later. When thecommand received from the address translation unit 62 requests to readdata (valid data) in a valid page with a specified physical blockaddress, the NAND controller 66 reads data written in a pagecorresponding to the physical block address in the semiconductor memoryelement 58 by using the physical block address, and stores the read datain the data buffer 67. When the command received from the CH allocatingunit 63 requests to write valid data, the NAND controller 66 retrieveswrite target valid data via the buffer controller 61 and writes thevalid data to the semiconductor memory element 58.

The compaction candidate detector 64 refers to the bit vector tableincluded in the management table 69, determines a logical block to be acandidate for compaction, and sends a command (referred to as compactionread command) specifying the physical block address of a valid page inthe logical block and requesting to read the valid page to thecompaction read queue 68.

The data buffer 67 is a buffer for storing the write target data. Thecompaction read queue 68 is a first-in first-out buffer that stores acommand requesting to read a valid page for compaction.

The buffer controller 61 manages the data buffer 67 as a plurality ofregions and manages the regions in which data corresponding to thecommand are stored. Concretely, the buffer controller 61 stores writetarget data sent from the host interface unit 60 in response to a writecommand into the data buffer 67, and sends the write target data to theNAND controller 66 corresponding to the channel determined to be writtenby the CH allocating unit 63. The write target data is written in thesemiconductor memory element 58 via the NAND controller 66. The buffercontroller 61 stores the data sent from the NAND controller 66 into aspecified region in the data buffer 67 in response to the read command,and then sends the data to the host interface unit 60. The data istransmitted to the host via the host interface unit 60. In response tothe compaction read command, the buffer controller 61 stores data readfrom the semiconductor memory element 58 via the NAND controller 66 intothe data buffer 67.

In the case where a command (write command) requesting to write datawith a specified logical block address is received from a host, themanagement table updating unit 65 refers to the forward-lookup table,updates the bit vector table, and further updates the forward-lookuptable. Concretely, the management table updating unit 65 first refers tothe forward-lookup table to look up the physical block addresscorresponding to the logical block address. Namely, the management tableupdating unit 64 looks up which page of the physical block the dataassociated with the logical address has been written in. If the physicalblock address associated with the logical block address is not stored inthe forward-lookup table, writing of data associated with the logicalblock address has not been performed. In this case, the management tableupdating unit 65 sets the value of the bit vector corresponding to thepage to which the write target data associated with the logical blockaddress is written in the bit vector table to “1”. The page to which thewrite target data is written is pointed by the write pointer. Themanagement table updating unit 65 increments the value of a counter ofthe number of valid pages in the logical block associated with thephysical block including the page by 1.

In contrast, if the physical block address associated with the logicalblock address exists in the forward-lookup table when the managementtable updating unit 65 refers to the forward-lookup table, writing ofthe data associated with the logical block address has been performedbefore. In this case, it is necessary to invalidate the data writtenbefore due to the write command for the present writing. For thispurpose, the management table updating unit 65 sets the value of the bitvector corresponding to the page at the physical block address stored inthe entries of the forward-lookup table referred to for the logicalblock address specified by the write command to “0”. In addition, themanagement table updating unit 65 decrements by 1 the value of a counterwhich indicates the number of valid pages in the logical block with thephysical block that includes the page. The management table updatingunit 65 sets the value of the bit vector corresponding to the page towhich the write target data is to be written to “1”, and increments by 1the value of a counter of the number of valid pages in a logical blockassociated with the physical block that includes the page. By performingupdating each time writing of data is performed, the bit vector tableand the counter of the number of valid pages always indicate thelocations of valid pages and the number thereof. Finally, the managementtable updating unit 65 records the physical block address to which writetarget data is written in an entry corresponding to the logical blockaddress in the forward-lookup table.

Next, procedures of processes performed by the semiconductor memorydevice 50 according to the embodiment will be described. First,procedures of writing the write target data in the semiconductor memoryelement 58 by the semiconductor memory device 50 in response to a writecommand from a host will be described with reference to FIG. 9. Beforestarting the writing, the semiconductor memory device 50 reserves freeblocks for channels in advance. When a write command requesting to writedata with a specified logical block address is received from the host(step S1), the semiconductor memory device 50 selects one free block ineach of the channels and constitutes a logical block by associating thefree blocks of the channels CH0 to CH5. When a write command requestingto write data with a specified logical block address is received fromthe host and there is no unwritten page left in the ongoing logicalblock, the semiconductor memory device 50 may secure the free block.When there is any unwritten pages left in the ongoing logical block, thesemiconductor memory device 50 does not secure the free block and writesthe data into the unwritten page in the logical block. The semiconductormemory device 50 gives a logical block number to the logical block andrecords the logical block number as an index and the respective physicalblock addresses, which are associated with the logical block, of thephysical blocks in the channels into a logical-to-physical translationtable. At this time, the semiconductor memory device 50 arranges thesorting order of logical-to-physical translation table entries, thesorting order of the physical block addresses of the physical blocks inthe channels in the logical-to-physical translation table entries, andbit vectors in a bit vector table so that a bit vector of each physicalblock associated with the logical block can be referred to by using theindex in the logical-to-physical translation table. The semiconductormemory device 50 sets, for each channel, the write pointer indicative ofa page of each physical block to which data is to be written, togetherwith the physical block address, which is associated with the logicalblock, in each physical block. Before starting writing, thesemiconductor memory device 50 sets the write pointer of each channel soas to point the first page of the physical block at the head of thechannel.

The semiconductor memory device 50 determines whether the size of datarequested to be written by the write command is equal to or less thanthe page size or not (step S2). In the case where the page size is equalto or less than the size of a page (YES in step S2), the semiconductormemory device 50 stores the data (write target data) in the data buffer67 (step S4). In contrast, in the case where the size of data requestedto be written by the write command is larger than the page size (NO instep S2), the semiconductor memory device 50 divides the data intopieces in units of a page (step S3) and records the divided pieces ofdata (write target data) into the data buffer 67 (step S4).

The semiconductor memory device 50 refers to the forward-lookup table onthe basis of a logical block address specified by the write command and,when a physical block address corresponding to the logical block addressof the write target data has been already recorded therein, thesemiconductor memory device 50 stores the physical block address as anold physical block address in the DRAM 54, for example (step S5). Thesemiconductor memory device 50 determines channels to which the writetarget data is to be written in round-robin manner (step S6) and writesthe write target data with a page ECC and the logical block addressadded thereto to a page pointed by the write pointer in thesemiconductor memory element 58 of the determined channel (step S7).Then, the semiconductor memory device 50 updates the write pointer ofeach channel to point a next unwritten page following the page to whichthe write target data is written (step S8).

FIG. 10 is a diagram showing a state where the divided pieces of data iswritten as write target data in the channel CH0 with lapse of time.First, at time t0, a free block is reserved. At time t1, first divideddata D1 is written in the first page (at the head or at the end) in thefree block reserved at time t0. At time t2, newly-determined divideddata D6 is written in the second page in the channel CH0 in theround-robin manner. Similarly, at time t3, divided data D11 is writtenin the third page. At time t4, divided data D16 is written in the fourthpage. In such a manner, pages to which divided pieces of data arewritten are determined in ascending order in the physical blockregardless of the logical block address. The write pointer is set eachtime writing is performed so as to point a page to which data is writtenin the ascending order. In the embodiment, writing operations to thechannels are performed uniformly in the round-robin manner, so that thedifference between the page numbers pointed by the write pointer in eachchannel is 1 at the maximum. When the writing is finished on the finalpage in the logical block, the page numbers pointed by the writepointers in the channels are the same.

As described above, regardless of the value of a logical block addressspecified by a write command from a host, the physical block addressesof pages to which write target data are allocated in a ascending order,and data is written in the pages.

The description refers back to FIG. 9. As write target data is written,the semiconductor memory device 50 records the association between thelogical block address of write target data and the physical blockaddress of the page to which the write target data is written into theforward-lookup table illustrated in FIG. 4 (step S9). If the writetarget data is divided pieces of data, the semiconductor memory device50 calculates each of the physical block addresses of the divided piecesof data on the basis of the logical block address specified by the writecommand. Since the divided pieces of data are in units of a page, thesemiconductor memory device 50 calculates values obtained bysequentially adding the page size (4 KB) to the specified logical blockaddress as the logical block addresses of the divided pieces of data.Then, the semiconductor memory device 50 records the logical blockaddress, the logical block number of the logical block associated withthe physical block of each of channels to which the write target data iswritten is associated, and the channel number and page number indicatingthe channel and page to which the write target data is written in thecurrent process into the LBA table. In the above-described example, thepage number is indicated by lower six bits of the write pointer beforeupdating, so that the value may be used as the page number. Each timewriting of write target data is performed, the semiconductor memorydevice 50 updates the forward-lookup table as described above.

Further, the semiconductor memory device 50 refers to the bit vectortable, sets the value of the bit vector corresponding to the page of theold physical block address stored in the DRAM 54 in step S5 to “0”, anddecrements the value of the counter of the number of valid pages of thelogical block associated with the physical block that includes the pageby 1 (step S10). The old physical block address indicates a page towhich data was previously written in association with the logical blockaddress specified by the write command received in step S10. Further,the semiconductor memory device 50 sets the value of the bit vectorcorresponding to the page to which the write target data is written instep S7 to “1”, and increments the value of the counter of the number ofvalid pages of the logical block that includes the page by 1 (step S11).In such a manner, the semiconductor memory device 50 updates the bitvector table as the write target data is written.

In step S7, after writing of the write target data to the channels CH0to CH4 is finished, the semiconductor memory device 50 calculates theexclusive OR in bytes at the same offset location in the write targetdata in the channels CH0 to CH4 and writes this value in the same offsetlocation in the channel CH5, thereby writing redundant information.Alternatively, the semiconductor memory device 50 may start calculatingthe exclusive OR while writing the write target data to the channels CH0to CH4.

In the case where the write pointer reaches the end of the block in allof the channels (CH0 to CH5) and data becomes unable to be newly writtenin the logical block, the semiconductor memory device 50 constructs anew logical block. A method of constructing a logical block is asdescribed above. A method of writing divided pieces of data andredundant information to the new logical block is also as describedabove.

Next, procedures of reading data from the semiconductor memory element58 by the semiconductor memory device 50 in accordance with a readcommand from a host will be described with reference to FIG. 11. When aread command requesting to read data with a specified logical blockaddress is received from the host (step S20), the semiconductor memorydevice 50 determines whether the size of data requested to be read bythe read command is equal to or less than the page size (step S21). Inthe case where the size of the data is equal to or less than the pagesize (YES in step S21), the semiconductor memory device 50 refers to theLBA table of the forward-lookup table by using the logical block addressspecified by the read command and determines the logical block number.Next, the semiconductor memory device 50 refers to a logical-to-physicaltranslation table by using the determined logical block number anddetermines a channel, a physical block and a page from which the data isto be read (step S23). The semiconductor memory device 50 reads the datafrom the semiconductor memory element 58 corresponding to the determinedchannel (step S24).

In contrast, in the case where the size of data requested to be read bythe read command is larger than the page size (NO in step S21), thesemiconductor memory device 50 divides reading so that data to be readbecomes pieces of data in page units. That is, the semiconductor memorydevice 50 calculates each of the logical block addresses of the piecesof data to be read by using the logical block address specified by theread command (step S22). The semiconductor memory device 50 refers tothe LBA table of the forward-lookup table and determines each of thelogical block numbers using each of the calculated logical blockaddresses. Next, the semiconductor memory device 50 refers to thelogical-to-physical translation table and determines each of thechannels, the physical blocks, and the page from which the data is to beread (step S23) using each of the determined logical block numbers. Thesemiconductor memory device 50 reads the pieces of data from thesemiconductor memory elements 58 corresponding to the determinedchannels (step S24).

Validity of the data read in step S24 is ensured by a page ECC added tothe data. That is, the semiconductor memory device 50 detects an errorin the data and can correct it by using the page ECC added to the readdata. However, when there may be an error that cannot be corrected withthe page ECC or miss-corrected with the page ECC, there is thepossibility that a failure occurs in the semiconductor memory element 58and abnormality occurs in data. In such a case (NO in step S25), thesemiconductor memory device 50 refers to the forward-lookup table,determines a logical block associated with the physical block of thechannel from which the data has been read using the logical blockaddress used in reading of data (step S27), reads other pieces of dataand redundant information written in the physical blocks of otherchannels associated with the determined logical block, and restores thedata including the uncorrectable error by using the other pieces of dataand the redundant information.

FIG. 12 is a diagram showing a state of restoring data which becomesabnormal due to a failure which occurs in the semiconductor memoryelement 58 of the channel CH3 as an example. Concretely, thesemiconductor memory device 50 reads the other pieces of data andredundant information (pieces of data written in the channels CH0, CH1,CH2, and CH4 and redundant information written in the channel CH5)written in the physical blocks of channels other than the physical blockassociated with the logical block determined in step S27 and thephysical block from which the erroneous data which cannot be correctedis read. The semiconductor memory device 50 restores the data in thechannel CH3 by obtaining the exclusive OR at the same offset in theother pieces of data and the redundant information, that is, theexclusive OR in bytes at the same offset location. The semiconductormemory device 50 stores the restored data in the data buffer 67 (stepS28) and advances to step S29.

Since there is a high possibility that abnormality occurs in a page fromwhich erroneous data is read, the semiconductor memory device 50 newlywrites the restored data to a different page. The semiconductor memorydevice 50 updates the bit vector table and the forward-lookup table byusing the logical block address used in reading of data. The method ofupdating the tables is as described above. As a result of the updating,the bit vector of the page from which erroneous data is read is updatedto “0”, the bit vector of the page in which the restored data is writtenis updated to “1”, and the physical block address of the page in whichthe restored data is written is recorded in a entry of theforward-lookup table for the logical block address specified by the readcommand.

In the case where there is no error in the data read in step S24, thesemiconductor memory device 50 stores the data in a specified region inthe data buffer 67 and advances to step S29. Even if there is an errorin data read in step S24, the semiconductor memory device 50 correctsthe data with the page ECC (step S26), stores the corrected data in aspecified region in the data buffer 67, and advances to step S29. Instep S29, the semiconductor memory device 50 transmits the data storedin the designated region in the data buffer 67 to the host.

When reading of a plurality of pieces of data is requested by a readcommand received in step S20, the semiconductor memory device 50 mayread data from physical blocks of channels associated with differentlogical blocks in accordance with logical block addresses specified bythe command. Since the channels can be independently accessed at thetime of reading data as described above, the data can be read inresponse to a request from the host and transmitted to the host withhigh responsibility.

Next, procedures of moving valid data written in a logical block to besubjected to compaction to a free block will be described with referenceto FIG. 13. The semiconductor memory device 50 sets “M=4096” as themaximum value of the number of valid pages, and sets “K=0” as an indexof an entry of each logical block in a bit vector table (step S40). Thesemiconductor memory device 50 sequentially reads the value of thecounter of the number of valid pages for each logical block one by oneby referring to the bit vector table (step S41) and determines whetherthe value of the counter is smaller than M or not (step S42). In thecase where the value of the counter of the number of valid pages isequal to or larger than M (NO in step S42), the device advances to stepS44. In the case where the value of the counter of the number of validpages is smaller than M (YES in step S42), the semiconductor memorydevice 50 replaces the value of M with the value of the counter and instep S41, sets the value of the index of the entry with which the valueof the counter of the number of valid pages is read as K (step S43), andadvances to step S44.

In step S44, the semiconductor memory device 50 determines whether ornot the value of the counter of the number of valid pages has been readwith respect to all of the logical blocks in the bit vector table. Inthe case where the value of the counter of the number of valid pages isread with respect to all of the logical blocks (NO in step S44), thesemiconductor memory device 50 increments the value of K by 1 (step S45)and returns to step S41. In step S41, the semiconductor memory device 50reads the value of the counter of the number of valid pages in thelogical blocks which are not read yet in the order of K in the bitvector table. In contrast, in the case where the value of the counter ofthe number of valid pages has been read with respect to all of thelogical blocks (YES in step S44), the semiconductor memory device 50sets the value of K as the index of a logical block as a candidate to besubjected to compaction in the logical-to-physical translation table(step S46). As described above, since the entries are arranged so thatthe bit vector table can be referred to using the index of thelogical-to-physical translation table, the index K of the entry in thebit vector table can be used as the index of the entry in thelogical-to-physical translation table. The semiconductor memory device50 determines data (valid data) stored in a page (valid page) whose bitvector in the bit vector table indicates “1” with respect to each of thephysical blocks in the channels CH0 to CH4 associated with the logicalblock of the entry indicated by the index K in the logical-to-physicaltranslation table and reads all of the valid data to the data buffer 67.The semiconductor memory device 50 extracts the logical block addressadded to the valid data (step S47).

The semiconductor memory device 50 writes each piece of the valid dataread in step S47 in a manner similar to the writing of data performed inresponse to the write command as described above. That is, thesemiconductor memory device 50 determines a channel to which the validdata is to be written from the channels CH0 to CH4 in the round-robinmanner and writes the valid data to a page indicated by the writepointer in an erased block in the semiconductor memory element 58 in thechannel. After that, the semiconductor memory device 50 updates thewrite pointer so as to point a next unwritten page following the page towhich the valid data is written. The redundant information is calculatedon the basis of the data written in the channels CH0 to CH4 and iswritten in the channel CH5. The semiconductor memory device 50 recordsthe association between the logical block address added to the writtenvalid data and the physical block address of the page in which the validdata is written into the forward-lookup table to update the table (stepS48). The method of updating the forward-lookup table is as describedabove. In the compaction, by updating the forward-lookup table, theassociation between the logical block address and the physical blockaddress of data can be always held normally. Since a logical blockaddress is added to data, the association between the logical blockaddress and a physical block address in which the data is written can beeasily updated in performing the compaction.

When reading from the data buffer 67 of data in all of valid pagesloaded to the data buffer 67 is finished (YES in step S49) and thewriting to the semiconductor memory element 58 is finished, thesemiconductor memory device 50 performs erasing operation on thephysical blocks in the channels CH0 to CH5 associated with the logicalblock as candidates to be subjected to compaction in step S46, andfinishes the compaction process.

The timing of performing the compaction process may be, for example, atiming when the number of free blocks that is obtained by a check uponconstitution of the logical block becomes equal to or less than apredetermined number.

As described above, in the configuration of using a plurality ofsemiconductor memory elements so that data can be accessed even when anyof the semiconductor memory elements is faulty, data is written on thepage unit basis. Data larger than the page size is divided in units of apage. After that, the divided pieces of data are allocated to thesemiconductor memory elements 58 and written to the pages in each of thesemiconductor memory elements 58 so that writing operations to thesemiconductor memory elements 58 are uniformly performed. By writingredundant information for data written to the pages in the plurality ofsemiconductor memory elements into pages of a single semiconductormemory element, an error correction code is constituted by the pages ofthe plurality of semiconductor memory elements. Data reading isperformed on the page unit basis and, when abnormality occurs in data,it is regarded that abnormality occurs in a page in a semiconductormemory elements 58 to which the data is written, data is restored byusing an error correction code constituted among the semiconductormemory device includes the abnormal page and the other semiconductormemory elements.

With such a configuration, with respect to writing of data to aplurality of pages (five pages in the above-described example), pagesused for writing of redundant information corresponding to the data canbe suppressed to fewer pages (one page in the above-described example)than used for writing of data. In contrast, in RAID of an HDD, withrespect to writing of data of one page, writing of redundant informationcorresponding to the data is one page. In the embodiment, the writing ofredundant information can be suppressed to 1/N (one fifth in theabove-described example). As described above, since the number ofwriting times is limited in a semiconductor memory element of an NANDtype, while suppressing the number of times of writing redundantinformation, the reliability of the semiconductor memory device 50 canbe improved.

In the RAID of an HDD, when abnormality occurs in data, it is regardedthat the entire HDD in which the data is stored becomes faulty, the HDDis detached, and the data is restored with an error correction codeconstituted among the HDD storing the fault data therein and other HDDs.In the embodiment, even when abnormality occurs in data, it can behandled as a failure of a block or a page as a part of the semiconductormemory element, not as a failure of the entire semiconductor memoryelement. Consequently, an error in a smaller unit can be also handled.Even when an entire semiconductor memory element becomes faulty, datawritten in the semiconductor memory element can be restored with anerror correction code constituted among the semiconductor memory elementstoring the fault data therein and other semiconductor memory elements.Therefore, extremely high reliability can be realized.

With such a configuration, even when abnormality occurs in data due to afailure or the like in a semiconductor memory element, the data can berestored with an error correction code. Consequently, the reliability ofthe semiconductor memory device 50 can be improved, and increase in thenumber of writing times of a semiconductor memory element which islimited can be suppressed.

In the embodiment, by providing the bit vector table, compaction can beefficiently performed at high speed. To perform compaction, thesemiconductor memory device 50 has to identify a valid page in whichvalid data is written in a block, obtain a logical block addresscorresponding to the valid page, move the valid data, and perform anupdating process of associating the logical block address with aphysical block address of a page to which the data is moved.Identification of a valid page and updating of a physical block addresscan be performed via a forward-lookup table. However, the forward-lookuptable is constituted by being optimized to a search using a logicalblock address as an index. Consequently, identification of a valid pageand updating of a physical block address via a forward-lookup table atthe time of performing compaction causes increase in penalty in searchtime.

A logical block subjected to be compaction has desirably small number ofvalid pages. This reason is that, by moving a valid page by compaction,a number of free blocks are obtained. To select a logical block havingsmall number of valid pages, an entry having small number of bit vectorshaving a value of “1” may be selected. To count the number of bitvectors having a value of “1”, for example, population computation(counting of the number of bits having a value of “1” in a word) may beprovided. However, when the bit width of an entry is large (320 bits inthe example), it is difficult to calculate the number of bits in onecycle. Consequently, in the embodiment, the semiconductor memory device50 updates the value of the counter of the number of valid pages shownin FIG. 5 in accordance with a change in the value of the bit vector. Atthe time of retrieving a logical block to be subjected to compaction, byretrieving an entry having the smallest number of the counter of validpages in the bit vector table, the logical block is obtained. An entryin which the value of the counter of the number of valid pages is thesmallest can be retrieved by once reading each of the values of thecounters of the number of valid pages of entries related to all oflogical blocks. Therefore, in the semiconductor memory device 50 in theembodiment, by referring to the bit vector table, a logical block havingsmall number of valid pages can be easily retrieved, and compaction canbe performed efficiently at high speed.

[Modifications]

The invention is not limited to the embodiment presented above, but maybe embodied with various modified components in implementation withoutdeparting from the spirit of the inventions. Further, the invention canbe embodied in various forms by appropriately combining a plurality ofcomponents disclosed in the embodiment. For example, some of thecomponents presented in the embodiment may be omitted. Further, somecomponents in different embodiments may be appropriately combined. Inaddition, various modifications as described as examples below may bemade.

In the above-described embodiment, various programs executed in thesemiconductor memory device 50 may be stored on a computer connected toa network such as the Internet, and provided by being downloaded via thenetwork. The various programs may be recorded in computer readablerecording medium such as a CD-ROM, a flexible disk (FD), a CD-R, or adigital versatile disk (DVD) in a form of a file that can be installedor executed, and provided as a computer program product.

In the above-described embodiment, a part of the function of theprocessor 51 may be implemented by hardware. The semiconductor memorydevice 50 may have a plurality of processors 51, and the above-describedfunctions may be implemented by the plurality of processors 51. Withsuch a configuration, higher processing speed can be achieved.

In the above-described embodiment, the forward-lookup table and the bitvector table are stored in the DRAM 54, but the invention is not limitedthereto. For example, the tables may be stored in the semiconductormemory element 58 and cached in the DRAM 54 when the tables are used bythe processor 51.

In the above-described embodiment, an ECC code is added to each data ina unit of a page as a page ECC. However, the ECC code may be added to aunit smaller than a page (for example, a unit of a sector of 512 bytes).With such a configuration, in the case where an error in data cannot becorrected in a unit smaller than a page, it may be regard thatabnormality occurs in the data and restore the data by using an errorcorrection code made by a plurality of channels.

In the above-described embodiment, a unit of constituting an errorcorrection code by a plurality of channels is set as a byte, but theinvention is not limited thereto and may use a size larger or smallerthan byte as a unit. Although a parity code is used as an errorcorrection code, the invention is not limited to the parity code. Aplurality of pieces of redundant information may be set and a ReedSolomon code may be used. With the Reed Solomon Code, data in whichabnormality occurs due to failures in a plurality of semiconductormemory elements 58 can be restored.

In the above-described embodiment, the number of channels to which datais written is four, the number of channels to which redundancyinformation for the data is written is one, and the number of channelsconstituting an error correcting code is five, but the invention is notlimited thereto. Further, in the above-described embodiment, the channelto which redundancy information constituting an error correcting code iswritten is fixed to the channel CH5, but the invention is not limited tothe channel. The channels may be allocated to units each constituting anerror correction code.

In the above-described embodiment, the channels correspond one-to-one tothe semiconductor memory elements 58, but the invention is not limitedthereto. The channels may correspond one-to-multiple to thesemiconductor memory elements 58, that is, a plurality of semiconductormemory elements 58 may be allocated to one channel. In this case,identification numbers for identifying the respective semiconductormemory elements 58 are allocated to the semiconductor memory elements58. The identification numbers and physical block addresses are recordedfor each block of each channel. For example, if eight semiconductormemory elements are allocated to each channel, a total of 15 bitsincluding 3 bits for identifying the semiconductor memory elements and12 bits for identifying 4,096 blocks included in each semiconductormemory element are recorded as the identification number and thephysical block address of each of blocks of each channel in thelogical-to-physical translation table.

In the foregoing embodiment, to simplify mounting of thelogical-to-physical translation table, desirably, the number of entriesin the logical-to-physical translation table and the number of blocks ineach channel. Since the number of entries on the logical-to-physicaltranslation table and the number of physical blocks in the channel CH0are equal to each other, the logical-to-physical translation table maybe constructed so that a location where an entry of a logical block isrecorded can be determined by the physical block number of the physicalblock in the channel CH0. The physical block numbers are given, forexample, in ascending order to physical blocks included in the channel.In this case, the physical block number of the physical block in thechannel CH0 may be set as the logical block number serving as an indexof the logical-to-physical translation table. Alternately, entries inthe logical-to-physical translation table may be recorded in a free liststructure.

In the above-described embodiment, the semiconductor memory device 50adds a logical block address to write target data in the semiconductormemory element 58. However, the semiconductor memory device 50 mayfurther include a physical-to-logical translation table (different fromthe logical-to-physical translation table) showing association betweenthe physical block address, as an index, of data written in thesemiconductor memory element 58 and the logical block address of thedata, instead of adding the logical block address. Then, in compaction,the semiconductor memory device 50 may use the physical block address ofvalid data read from the semiconductor memory element 58, refer to thephysical-to-logical translation table to obtain the logical blockaddress corresponding to the physical block address, and update theforward-lookup table as a result of compaction using the obtainedlogical block address.

In the above-described embodiment, when allocating channels to the writetarget data, in the case where a state where there is no write targetdata continues for predetermined time after allocating data to at leastone of the channels CH0 to CH3, dummy data (for example, data whose bitsare all “0”) in a corresponding page in a channel to which the writetarget data is not allocated out of the channels CH1 to CH4, andredundant information calculated by using data in corresponding pages inthe channels CH1 to CH4 is written in the corresponding page in thechannel CH5. With such a configuration, the possibility such that anerror correction code is not constituted for data in a channel to whichdata has been already written in corresponding pages in the channels CH0to CH4 and, when an error occurs in the data, the data cannot berestored can be avoided.

According to the present invention, while suppressing increase in thenumber of times of writing data to semiconductor memory chips, a failurein the semiconductor memory chips can be addressed, and reliability canbe improved.

While certain embodiments have been described, these embodiments havebeen presented by way of example only, and are not intended to limit thescope of the inventions. Indeed, the novel embodiments described hereinmay be embodied in a variety of other forms; furthermore, variousomissions, substitutions and changes in the form of the embodimentsdescribed herein may be made without departing from the spirit of theinventions. The accompanying claims and their equivalents are intendedto cover such forms or modifications as would fall within the scope andspirits of the inventions.

What is claimed is:
 1. A controller that writes data into a plurality ofsemiconductor memory chips, the data having N pieces of first data in apredetermined unit, the controller comprising: a write controllerconfigured to write each of the N pieces of the first data andredundancy information into different semiconductor memory chips, theredundancy information by using the written N pieces of the first data,each of the N pieces of the first data including page error correctinginformation, which detects and corrects a memory error; and a storageunit configured to store therein identification information and regionspecifying information so as to be associated with each other, theidentification information associating the N pieces of the first dataand the redundancy information, and the region specifying informationspecifying a plurality of storage regions in the semiconductor memorychips to which the N pieces of the first data and the redundancyinformation associated with each other are written, wherein theredundancy information is obtained by calculating an exclusive OR inbytes at respective corresponding offset locations in the N pieces ofthe first data, and when the memory error is not corrected by using thepage error correcting information, each of the N pieces of the firstdata is restored by calculating an exclusive OR in bytes at respectivecorresponding offset locations in the redundant information andremaining pieces of the first data.
 2. A controlling method for writingdata into a plurality of semiconductor memory chips, the data having Npieces of first data in a predetermined unit, the method comprising:writing each of the N pieces of the first data and redundancyinformation into different semiconductor memory chips, and calculatingthe redundancy information by using the written N pieces of the firstdata, each of the N pieces of the first data including page errorcorrecting information, which detects and corrects a memory error; andstoring identification information and region specifying information soas to be associated with each other, the identification informationassociating the N pieces of the first data and the redundancyinformation, and the region specifying information specifying aplurality of storage regions in the semiconductor memory chips to whichthe N pieces of the first data and the redundancy information associatedwith each other are written, wherein the redundancy information isobtained by calculating an exclusive OR in bytes at respectivecorresponding offset locations in the N pieces of the first data, andwhen the memory error is not corrected by using the page errorcorrecting information, each of the N pieces of the first data isrestored by calculating an exclusive OR in bytes at respectivecorresponding offset locations in the redundant information andremaining pieces of the first data.